PCI multi-seg: add new physdevop-s
authorJan Beulich <jbeulich@suse.com>
Sat, 17 Sep 2011 23:12:19 +0000 (00:12 +0100)
committerJan Beulich <jbeulich@suse.com>
Sat, 17 Sep 2011 23:12:19 +0000 (00:12 +0100)
commit7620c0cf9a4df9cff19be020bf84f8a71cc31d8d
tree4e0695f43d0d1ad85c0fcaf1a4d59fb5b7859740
parent21844b0e32e77c9e1a600b9279a859a7ffe01844
PCI multi-seg: add new physdevop-s

The new PHYSDEVOP_pci_device_add is intended to be extensible, with a
first extension (to pass the proximity domain of a device) added right
away.

A couple of directly related functions at once get adjusted to account
for the segment number.

Should we deprecate the PHYSDEVOP_manage_pci_* sub-hypercalls?

Signed-off-by: Jan Beulich <jbeulich@suse.com>
15 files changed:
xen/arch/ia64/xen/hypercall.c
xen/arch/x86/irq.c
xen/arch/x86/msi.c
xen/arch/x86/physdev.c
xen/arch/x86/x86_64/physdev.c
xen/drivers/passthrough/amd/pci_amd_iommu.c
xen/drivers/passthrough/iommu.c
xen/drivers/passthrough/pci.c
xen/drivers/passthrough/vtd/iommu.c
xen/drivers/passthrough/vtd/quirks.c
xen/drivers/passthrough/vtd/x86/ats.c
xen/include/asm-x86/msi.h
xen/include/public/physdev.h
xen/include/xen/pci.h
xen/include/xlat.lst